Save MCP Server

Used to create or update an MCP (Model Context Protocol) server. This allows you to register MCP server metadata in your project, enabling integration with external services and tools that support the Model Context Protocol.

API Endpoint

Property	Value
Request Method	POST
Request URL	https://api.seliseblocks.com/tools/mcp-server

Request

Request Example

curl -X POST 'https://api.seliseblocks.com/tools/mcp-server' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "id": "mcp_server_123",
    "name": "Customer Data Server",
    "description": "MCP server for accessing customer data and analytics",
    "project_key": "YOUR_PROJECT_KEY"
  }'

Request Headers

Field	Type	Required	Description
accept	string	Yes	Accepted response format. Use application/json
Content-Type	application/json	Yes	Data type, must be application/json.

Request Body

Request Body Schema

{
  "id": "string",
  "name": "string",
  "description": "string",
  "project_key": "string"
}

Request Body Parameters

Field	Type	Required	Description
id	string	Yes	Unique identifier for the MCP server.
name	string	Yes	Display name of the MCP server.
description	string	Yes	Detailed description of the MCP server's purpose and functionality.
project_key	string	Yes	The project key for your project.

note

MCP Server Configuration

• id: Use a unique, descriptive identifier for the MCP server
• name: Should be human-readable and clearly identify the server's purpose
• description: Provide context about what data or services the MCP server provides
• This endpoint saves metadata only; actual MCP server connection details are configured separately

tip

After saving an MCP server, the system will:

• Create a new MCP server entry if the ID doesn't exist
• Update the existing MCP server if the ID already exists
• Associate the server with the specified project
• Make the server available for use with AI agents in the project
• Validate that all required fields are provided

Response

Success Response (201 Created)

Returns an object containing the save status.

{
  "is_success": true,
  "item_id": "mcp_server_123",
  "detail": "MCP server saved successfully",
  "error": {}
}

Response Fields

Field	Type	Description
is_success	boolean	Indicates whether the operation was successful.
item_id	string	The identifier of the saved MCP server.
detail	string	Success or failure message with additional context.
error	object	Error details if the operation failed (empty if successful).

Error Response (422 Unprocessable Entity)

Returns validation error details when the request body is invalid.

{
  "detail": [
    {
      "loc": [
        "body",
        "project_key"
      ],
      "msg": "field required",
      "type": "value_error.missing"
    }
  ]
}

Error Response Fields

Field	Type	Description
detail	array	Array of validation error objects.
loc	array	Location of the error in the request (e.g., body field).
msg	string	Human-readable error message.
type	string	Error type identifier.

Error Codes

Status Code	Description	Response Type
201	Created - MCP server saved successfully	Success
400	Bad Request - Invalid MCP server data	Bad Request
409	Conflict - MCP server ID already exists	Conflict
422	Validation Error - Invalid request parameters	Unprocessable Entity